Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1416

reference
697-tree-1
name
1416
tree-preservation-order

undefined

697-tpo-1
uprn
address-text
point
POINT (-1.010140 50.881494)
geometry
MULTIPOLYGON (((-1.010112 50.881491,-1.010113 50.881496,-1.010117 50.881501,-1.010123 50.881505,-1.010131 50.881508,-1.010140 50.881509,-1.010157 50.881506,-1.010163 50.881502,-1.010167 50.881497,-1.010169 50.881491,-1.010168 50.881486,-1.010164 50.881481,-1.010150 50.881474,-1.010141 50.881473,-1.010124 50.881476,-1.010118 50.881480,-1.010114 50.881485,-1.010112 50.881491)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL